Search results for "Software prototyping"

showing 8 items of 8 documents

Evolutionary White-Box Software Test with the EvoTest Framework: A Progress Report

2009

Evolutionary white-box software testing has been extensively researched but is not yet applied in industry. In order to investigate the reasons for this, we evaluated a prototype version of a tool, representing the state-of-the-art for evolutionary structural testing, which is targeted at industrial use. The focus was on the applicability of the structural test tool in the industrial context and not on assessment of the test cases generated. Four case studies, each consisting of an embedded software module from the automotive industry implemented in the C language, were evaluated with the tool. The case studies had to be customized to cope with the limitations of the tool and in all, test c…

Embedded softwareTest caseSoftwareComputer sciencebusiness.industryWhite-box testingSystems engineeringSystem testingSoftware prototypingWhite boxSoftware engineeringbusinessEvolutionary computation2009 International Conference on Software Testing, Verification, and Validation Workshops
researchProduct

Software Modernization Decision Criteria: An Empirical Study

2005

Decisions regarding software evolution strategies such as modernizations are economically important. We present results of our empirical study of the views of decision makers. We have asked their views of the relative importance of 49 software modernization decision criteria. We have gathered data from Finnish software industry. There were 26 experts from 8 organizations involved. They were mainly upper or middle level managers. Our study shows that there is a large set of criteria which should be taken into account, and that those studied by us provide a good coverage of the relevant ones. We list the top-20 criteria. We also performed a cluster analysis which produced two groups of subjec…

EngineeringSoftwareKnowledge managementSoftware modernizationEmpirical researchbusiness.industryInformation technologySoftware maintenanceSoftware prototypingMultiple-criteria decision analysisbusinessSoftware evolutionNinth European Conference on Software Maintenance and Reengineering
researchProduct

Hardware and firmware developments for the upgrade of the ATLAS Level-1 Central Trigger Processor

2014

The Central Trigger Processor (CTP) is the final stage of the ATLAS first level trigger system which reduces the collision rate of 40 MHz to a Level-1 event rate of 100 kHz. An upgrade of the CTP is currently underway to significantly increase the number of trigger inputs and trigger combinations, allowing additional flexibility for the trigger menu. We present the hardware and FPGA firmware of the newly designed core module (CTPCORE+) module of the CTP, as well as results from a system used for early firmware and software prototyping based on commercial FPGA evaluation boards. First test result from the CTPCORE+ module will also be shown.

Event (computing)business.industryComputer scienceFirmwareSoftware prototypingcomputer.software_genreUpgrademedicine.anatomical_structureTrigger concepts and systems (hardware and software)Atlas (anatomy)medicineLevel triggerDetectors and Experimental TechniquesField-programmable gate arraybusinessInstrumentationcomputerDigital electronic circuitsMathematical PhysicsComputer hardwareCollision rateJournal of Instrumentation
researchProduct

Communication Interface Generation For HW/SW Architecture In The STARSoC Environment

2006

Mapping the application functionality to software and hardware requires automated methods to specify, generate and optimize the hardware, software, and the interface architectures between them. In this paper, we present a methodology flow to hardware-software communication synthesis for system-on-a-chip (SoC) design through STARSoC (Synthesis Tool for Adaptive and Reconfigurable System-on-a-Chip) tool for rapid prototyping. Our concept consists of a set of hardware and software processes, described in C-code, communicates through the streams channels. This methodology consists in analyzing dependences of data between processes and synthesis a custom architecture to interface it. Firstly, we…

Hardware architectureResource-oriented architectureComputer sciencebusiness.industryInterface (computing)Software prototypingcomputer.software_genreSoftware frameworkComputer architectureEmbedded systemComponent-based software engineeringReference architecturebusinesscomputerFPGA prototype2006 IEEE International Conference on Reconfigurable Computing and FPGA's (ReConFig 2006)
researchProduct

Technical Briefing: Hands-On Session on the Development of Trustworthy AI Software

2021

Following various real-world incidents involving both purely digital and cyber-physical Artificial Intelligence (AI) systems, AI Ethics has become a prominent topic of discussion in both research and practice, accompanied by various calls for trustworthy AI systems. Failures are often costly, and many of them stem from issues that could have been avoided during development. For example, AI ethics issues, such as data privacy are currently highly topical. However, implementing AI ethics in practice remains a challenge for organizations. Various guidelines have been published to aid companies in doing so, but these have not seen widespread adoption and may feel impractical. In this technical …

Information privacyComputer sciencebusiness.industryCyber-physical systemTrusted ComputingSoftware maintenanceSoftware prototypingGeneralLiterature_MISCELLANEOUSSession (web analytics)Engineering managementComputingMethodologies_PATTERNRECOGNITIONbusinessDesign methodsAgile software development2021 IEEE/ACM 43rd International Conference on Software Engineering: Companion Proceedings (ICSE-Companion)
researchProduct

Defining Components in a MetaCASE Environment

2000

In this paper we describe how to improve method reusability in a metaCASE environment called MetaEdit+. The suggested component based approach helps unify design artefacts into components with explicit interfaces and meaningful context descriptions. We describe a method artefact from three perspectives: concept, content, and context. We create a component concept by using a hierarchical facet-based schema, and represent contextual relationship types by using definitional and reuse dependency, usage context, and implementation context links. This is the first attempt to explicitly define components into a metaCASE environment.

Object-oriented programmingDatabasebusiness.industryComputer scienceSoftware developmentSoftware prototypingReusecomputer.software_genreHuman–computer interactionSchema (psychology)Information systembusinesscomputerReusability
researchProduct

Towards Understanding of Software Engineer Motivation in Globally Distributed Projects

2011

Motivation in software engineering is reported to be a source for performance improvement, which leads to project overall success. Since it is a soft factor and difficult to quantify it is usually neglected. Research in this field is rather scarce and outdated. On the basis of a recent systematic review of software engineers' motivation we set an agenda for further investigation of the role of motivation in contemporary projects. As software organizations nowadays seek opportunities inherited in both - global software development (GSD) and agile projects, it is important to understand how different project environments influence motivation.

Social software engineeringEngineeringKnowledge managementbusiness.industryTeam software processPersonal software processSoftware developmentSoftware prototypingProject managementbusinessSoftware project managementAgile software development2011 IEEE Sixth International Conference on Global Software Engineering Workshop
researchProduct

Embracing iterations in Quantum software: a vision

2022

In today’s software engineering, iterations, affordable en masse, form an important part of just about any system. However, not all computing resources are cheap to consume. In High-Performance (HPC) and Quantum Computing (QC), executions can consume considerable amounts of energy and time, which is reserved and used even if the very first steps in the process fail. This means that developers must assume a different attitude towards programming, and aim at error-free software before its execution. This is com monly facilitated using simulators, which are commonplace for both HPC and QC. However the fashion developers advance from one tool to another is ad-hoc, with no established software e…

quantum software engineeringiterointiohjelmistosuunnittelusoftware prototypingohjelmistotuotantosimulointiquantum computing quantum IDEkvanttilaskentaohjelmistokehityssoftware development techniquesProceedings of the 1st International Workshop on Quantum Programming for Software Engineering
researchProduct